A Pattern for Modeling Rework in Software Development Processes
Identifieur interne : 003A28 ( Main/Exploration ); précédent : 003A27; suivant : 003A29A Pattern for Modeling Rework in Software Development Processes
Auteurs : Aaron G. Cass [États-Unis] ; Leon J. Osterweil [États-Unis] ; Alexander Wise [États-Unis]Source :
- Lecture Notes in Computer Science [ 0302-9743 ]
Abstract
Abstract: It is usual for work completed at one point in a software development process to be revisited, or reworked, at a later point. Such rework is informally understood, but if we hope to support reasoning about, and partial automation of, software development processes, rework be more formally understood. In our experience in designing formalized processes in software development and other domains, we have noticed a recurring process pattern that can be used to model rework quite successfully. This paper presents that pattern, which models rework as procedure invocation in a context that is carefully constructed and managed. We present some scenarios drawn from software engineering in which rework occurs. The paper presents rigorously defined models of these scenarios, and demonstrates the applicability of the pattern in constructing these models.
Url:
DOI: 10.1007/978-3-642-01680-6_28
Affiliations:
Links toward previous steps (curation, corpus...)
- to stream Istex, to step Corpus: 003B90
- to stream Istex, to step Curation: 003B46
- to stream Istex, to step Checkpoint: 000B36
- to stream Main, to step Merge: 003B07
- to stream Main, to step Curation: 003A28
Le document en format XML
<record><TEI wicri:istexFullTextTei="biblStruct"><teiHeader><fileDesc><titleStmt><title xml:lang="en">A Pattern for Modeling Rework in Software Development Processes</title><author><name sortKey="Cass, Aaron G" sort="Cass, Aaron G" uniqKey="Cass A" first="Aaron G." last="Cass">Aaron G. Cass</name></author><author><name sortKey="Osterweil, Leon J" sort="Osterweil, Leon J" uniqKey="Osterweil L" first="Leon J." last="Osterweil">Leon J. Osterweil</name></author><author><name sortKey="Wise, Alexander" sort="Wise, Alexander" uniqKey="Wise A" first="Alexander" last="Wise">Alexander Wise</name></author></titleStmt><publicationStmt><idno type="wicri:source">ISTEX</idno><idno type="RBID">ISTEX:F9FB74F6D38AFDCDE567B896E9433908F163E258</idno><date when="2009" year="2009">2009</date><idno type="doi">10.1007/978-3-642-01680-6_28</idno><idno type="url">https://api.istex.fr/ark:/67375/HCB-TM5CXL64-P/fulltext.pdf</idno><idno type="wicri:Area/Istex/Corpus">003B90</idno><idno type="wicri:explorRef" wicri:stream="Istex" wicri:step="Corpus" wicri:corpus="ISTEX">003B90</idno><idno type="wicri:Area/Istex/Curation">003B46</idno><idno type="wicri:Area/Istex/Checkpoint">000B36</idno><idno type="wicri:explorRef" wicri:stream="Istex" wicri:step="Checkpoint">000B36</idno><idno type="wicri:doubleKey">0302-9743:2009:Cass A:a:pattern:for</idno><idno type="wicri:Area/Main/Merge">003B07</idno><idno type="wicri:Area/Main/Curation">003A28</idno><idno type="wicri:Area/Main/Exploration">003A28</idno></publicationStmt><sourceDesc><biblStruct><analytic><title level="a" type="main" xml:lang="en">A Pattern for Modeling Rework in Software Development Processes</title><author><name sortKey="Cass, Aaron G" sort="Cass, Aaron G" uniqKey="Cass A" first="Aaron G." last="Cass">Aaron G. Cass</name><affiliation></affiliation><affiliation wicri:level="1"><country wicri:rule="url">États-Unis</country></affiliation></author><author><name sortKey="Osterweil, Leon J" sort="Osterweil, Leon J" uniqKey="Osterweil L" first="Leon J." last="Osterweil">Leon J. Osterweil</name><affiliation wicri:level="4"><orgName type="university">Université du Massachusetts à Amherst</orgName><country>États-Unis</country><placeName><settlement type="city">Amherst (Massachusetts)</settlement><region type="state">Massachusetts</region></placeName></affiliation><affiliation wicri:level="1"><country wicri:rule="url">États-Unis</country></affiliation></author><author><name sortKey="Wise, Alexander" sort="Wise, Alexander" uniqKey="Wise A" first="Alexander" last="Wise">Alexander Wise</name><affiliation wicri:level="4"><orgName type="university">Université du Massachusetts à Amherst</orgName><country>États-Unis</country><placeName><settlement type="city">Amherst (Massachusetts)</settlement><region type="state">Massachusetts</region></placeName></affiliation><affiliation wicri:level="1"><country wicri:rule="url">États-Unis</country></affiliation></author></analytic><monogr></monogr><series><title level="s" type="main" xml:lang="en">Lecture Notes in Computer Science</title><idno type="ISSN">0302-9743</idno><idno type="eISSN">1611-3349</idno><idno type="ISSN">0302-9743</idno></series></biblStruct></sourceDesc><seriesStmt><idno type="ISSN">0302-9743</idno></seriesStmt></fileDesc><profileDesc><textClass></textClass></profileDesc></teiHeader><front><div type="abstract" xml:lang="en">Abstract: It is usual for work completed at one point in a software development process to be revisited, or reworked, at a later point. Such rework is informally understood, but if we hope to support reasoning about, and partial automation of, software development processes, rework be more formally understood. In our experience in designing formalized processes in software development and other domains, we have noticed a recurring process pattern that can be used to model rework quite successfully. This paper presents that pattern, which models rework as procedure invocation in a context that is carefully constructed and managed. We present some scenarios drawn from software engineering in which rework occurs. The paper presents rigorously defined models of these scenarios, and demonstrates the applicability of the pattern in constructing these models.</div></front></TEI><affiliations><list><country><li>États-Unis</li></country><region><li>Massachusetts</li></region><settlement><li>Amherst (Massachusetts)</li></settlement><orgName><li>Université du Massachusetts à Amherst</li></orgName></list><tree><country name="États-Unis"><noRegion><name sortKey="Cass, Aaron G" sort="Cass, Aaron G" uniqKey="Cass A" first="Aaron G." last="Cass">Aaron G. Cass</name></noRegion><name sortKey="Osterweil, Leon J" sort="Osterweil, Leon J" uniqKey="Osterweil L" first="Leon J." last="Osterweil">Leon J. Osterweil</name><name sortKey="Osterweil, Leon J" sort="Osterweil, Leon J" uniqKey="Osterweil L" first="Leon J." last="Osterweil">Leon J. Osterweil</name><name sortKey="Wise, Alexander" sort="Wise, Alexander" uniqKey="Wise A" first="Alexander" last="Wise">Alexander Wise</name><name sortKey="Wise, Alexander" sort="Wise, Alexander" uniqKey="Wise A" first="Alexander" last="Wise">Alexander Wise</name></country></tree></affiliations></record>Pour manipuler ce document sous Unix (Dilib)
EXPLOR_STEP=$WICRI_ROOT/Wicri/Lorraine/explor/InforLorV4/Data/Main/Exploration
HfdSelect -h $EXPLOR_STEP/biblio.hfd -nk 003A28 | SxmlIndent | more
Ou
HfdSelect -h $EXPLOR_AREA/Data/Main/Exploration/biblio.hfd -nk 003A28 | SxmlIndent | more
Pour mettre un lien sur cette page dans le réseau Wicri
{{Explor lien
|wiki= Wicri/Lorraine
|area= InforLorV4
|flux= Main
|étape= Exploration
|type= RBID
|clé= ISTEX:F9FB74F6D38AFDCDE567B896E9433908F163E258
|texte= A Pattern for Modeling Rework in Software Development Processes
}}
| This area was generated with Dilib version V0.6.33. |  |